DataFlow/C++: fieldFlowBranchLimit follow-up (2)
#16303
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…branch' metrics in dataflow. These should no longer be needed now that we have second-level scopes.
MathiasVP
force-pushed
the
fieldflowbranchlimit-follow-up-2
branch
from
220ad54 to
d396a0b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gets rid of the
getAdditionalFlowIntoCallNodeTermhook we added as part of #12236. This shouldn't be needed anymore now that we've added second-level scopes in db6d27b 🤞Currently in draft while I run QA for it